Skip to content

Track default vs explicit http client usage#6849

Open
dagnir wants to merge 1 commit intomasterfrom
dongie/http-client-origin-md
Open

Track default vs explicit http client usage#6849
dagnir wants to merge 1 commit intomasterfrom
dongie/http-client-origin-md

Conversation

@dagnir
Copy link
Copy Markdown
Contributor

@dagnir dagnir commented Apr 8, 2026

Motivation and Context

Add metadata in the UA to track whether the HTTP client in use by the service client was picked up by default, or explicitly configured by the user.

This will help us understand how many customers rely on default http clients vs explicit configuration.

Modifications

Testing

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Checklist

  • I have read the CONTRIBUTING document
  • Local run of mvn install succeeds
  • My code follows the code style of this project
  • My change requires a change to the Javadoc documentation
  • I have updated the Javadoc documentation accordingly
  • I have added tests to cover my changes
  • All new and existing tests passed
  • I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
  • My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

  • I confirm that this pull request can be released under the Apache 2 license

Add metadata in the UA to track whether the HTTP client in use by the
service client was picked up by default, or explicitly configured by the
user.
@dagnir dagnir requested a review from a team as a code owner April 8, 2026 22:27
@dagnir dagnir added the no-api-surface-area-change Indicate there is no API surface area change and thus API surface area review is not required label Apr 8, 2026
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Apr 8, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-api-surface-area-change Indicate there is no API surface area change and thus API surface area review is not required

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant